FS2002 Generic Advanced Panel by Guy De Smet and Nick Pike.
-------------------------------
Nick: n.pike@blueyonder.co.uk
Guy : guydesmet@prodigy.net.mx
for comments and suggestions, including constructive critics.
Landing an ILS Approach.
-------------------------
Center joystick for best results.
Set ILS frequency on Nav 1 radio. A quick way is to use the rwy info gauge. Enter the ICAO abbreviation for the airport and double click the runway you want to land on. This will set the radios. Set the speed on the AP to about 160 kts and deploy the canards. Then deploy the gear. Set altitude to 3000 feet above the airport elevation to intercept the glide slope from below (definitely NOT from above - standard FS2002 procedure). Select approach button when HSI indicates you are receiving ILS signals (solid magenta bar first then magenta bug). A reassuring, self leveling slight bank indicates that the aircraft has locked onto ILS. Attempt to be fairly well lined up with the runway before you activate ILS. Reset speed to 140 kts before the ILS glide slope takes control, and then when under this control, reset speed to 120 kts for landing. As John Whiting says, "Don't be shooting landings with a gazillion gallons of fuel onboard"! If the AoA looks too high on finals, then there is probably too much fuel (weight) on board. Use the 25% fuel dump gauge on the fuel management panel to set an ideal landing weight.
The flaps, spoilers and gear are designed to produce drag for landing speeds
Therefore the maximum speeds with these deployed will be about 145 for 2 Engines less than
200,000 Lbs weight
Therefore the maximum speeds with these deployed will be about 165 for 2 and 3 Engines less
than 250,000 Lbs weight
Therefore the maximum speeds with these deployed will be about 180 for 4 Engines more than
250,000 Lbs weight
Additional Panel Notes
======================
I'm not going to give details on all gauges because of the quantity. All gauges have
tool tips, some with extra information where required, so the user should be able to work
out what a gauge is and how to use it.
The panel display also the model and type of airplane under the PFD and radar gauge.
The panel display also the Flight number, Atc_Id and the airline name in the upper left of the main panel.
If the display of this information here mentioned is incomplete, it is due that the
designer of the airplane did not declare the information in the aircraft.cfg. You may
add it yourself, The variables are:
The cruice_speed means more the maximum speed before overspeed. Some of the designer do
not take care of this parameter mostly of this last one, because it is used to prevent you
against overspeed. If it is not in the aircraft.cfg, the information is collected form the
model.mdl. You may change the cruise_speed value if necessary.
The HSI has a built in relative wind direction needle and speed value which only shows
when there is any wind. We have an additional gauges in the down center of the main panel.
It mention the wind speed in km/hr and knots and the direction, the red point is the airplane.
The decision height gauge is adjustable.
The autotrim is auto off and not available when the AP is on, as AP adjusts the trim when
in AP flight.
The pushback moves the aircraft rearwards. When moving rearwards, hit the '1' keyboard key
for tail left and '2' for right. Click on pushback again to stop. There are no sounds with pushback.
With the radio panel open, you can click on the appropriate memory field to memorize
frequency. Click on this again to set frequency in the appropriate radio. Click on the
appropriate clear area to clear the frequency from memory. A number of frequencies can be
stored. The 'E' icon on the radio will set the emergency communication frequency.
The AP windows (speed, altitude, heading and VS) can be zeroed by clicking in the left
hand end of the windows.
The altitude value can be increased or decreased in steps of 100 or 1000 according to
the '+' area clicked in the selector gauge.
The view can be panned by clicking on the appropriate areas on the general aircraft
information gauge (positioned in the top left corner of the main panel) which shows the
simplified picture of the aircraft.
Timer/Alarm. You can click for Local or Zulu time mode, and also for Stop watch type timer
which can be started, stopped and reset back to zero. To set the time alarm (Local or
Zulu), set the required alarm time in the alarm window, and click the bell icon in the
right corner of the overhead panel. You can leave the clock displaying or close it. If
closed, for example, when the alarm time is reached, the clock will redisplay and an
additional flashing warning will display and an alarm sound will play. To switch off the
alarm, click on the bell icon again. The alarm numbers will show green if the alarm set
time numbers are ahead of the clock time, and yellow if equal to or behind the clock time. For timer alarm, set the required elapsed time in the alarm window, start the timer and click the bell icon to activate the alarm. Again, the clock can be left displayed or closed. Actually, the bell icon can be clicked before setting or after. It does not matter when as it works by comparing the alarm setting with the time or timer numbers.
The Terrain follow gauge does not really suit for any aircraft type, but I added it for
some additional fun. When set, the aircraft attempts to follow the terrain topography
at a fixed radio height. This would be better suited to a fast military jet for low level
flight.
Set the required radio height in the altitude window, and switch on the TF gauge.
The AP should be on for speed, heading, altitude (and VS), that is, normal AP operation.
The set height should not be less than approximately 500 feet. The way FS2002 operates is
not perfect for this, and the height will vary by a few hundred feet. Also, FS2002 cannot
read ground heights in front of the aircraft. Occasionally you will come across ground
that is very steep (i.e. high hills) and the aircraft cannot climb fast enough to clear
the obstacle and would crash into it. When the ground clearance is less than 200 feet,
slew will automatically switch on and the aircraft will rise vertically to the ground
clearance set and then switch slew off automatically to continue flying and clear the high
ground. If one attempt is not enough, it will repeat the process until clearance is
achieved. There is not much point in using this for mountainous areas. The gauge can also
be used for a quick launch, that is, set the height in the altitude window when on the
ground, and the other required parameters in the AP, switch on and the aircraft will rise
vertically in slew mode until the required radio height is achieved and then fly on
normally.
Issues
------
The XML gauges do not illuminate conventionally on the DVC view at night.
Credits.
--------
Arne Bartels for a lot of help with the XML coded gauges, for supplying code for several gauges and for the fuel dump gauge compiling files. Also for bothering to explain how a lot of this code works. Many thanks Arne, you've been a massive help.
Chuck Dome for the code to the autotrim gauge and for producing the custom radio audio panel. Many thanks Chuck.
Ernie Alston for producing the custom Runway Info gauge and for producing such a useful gauge anyway. Well done Ernie.
Bill Morad for the custom gauge to produce a sound set for this aircraft. A very clever method of using FS variables in XML code to call up wav files. Thanks Bill, and thanks for your prompt and enthusiastic attention.
Tony D'AMBROSIO for the use of the FMC gauge.
Eric Marciano and Jorge Salas for the AI aircraft radar gauge.
Björn Karlsson for is generic take off and landing
Vladimir Sokolov for xml advice.
TIM ADAMS for being the chief test pilot, crash dummy and tyre kicker, flying many, many hours with this aircraft and giving very reliable feedback. Also for his generous enthusiasm and support. This project would have been far more difficult without this help. Many thanks Tim, and I look forward to working together on future projects (Mach 5.0 private aircraft?, who knows).
Matthias Lieberecht for general panel advice.
AcSoft of Switserland for the ACS-GPS, we are using the Concorde version, it is
recomended to check the website of the author for the last update. http://www.acsoft.ch
Pete Dowson for the useful FSUIPC package.
Daniel Steiner for the useful FSSound.dll file.
FPDA for the callout gauge.
If I have left anyone out, my apologies, and thanks.
Legalities.
-----------------
This panel package is supplied as Freeware and the associated copyright details apply.
No financial gain should be made with it and it must not be used on a CD compilation.
No modification for distribution without the permission of one of the 2 authors.
Ask permission for use of any component of this panel package, including any XML coding.
Use at your own risk. We are in no way responsible for anything that happens to you,
your software or your hardware equipment as a result of using these files.
I hope you enjoy flying this aircraft.
Guy De Smet and Nick Pike. The both authors.
Belgium/Mexico and UK.
